In the management console under 39Tools Embedded Scripts39 click 39New39 and give the script a descriptive name e.g. 39scriptname.ps139 and in the 39Script Content39 box add your script In the 39Interpreter field39 select 39powershell.exe inputformat none file39 from the dropdown and click 39OK39 Under 39System Health Packages39 create ...

KB-ID 396
Category: Application Scheduler
Applies to: 3.5 and later

For any Process action or Application Scheduler object in EventSentry you can use a nonembedded script by providing the full path to the script file i.e. C:\Batch\powershellscript.ps1. In many cases it is however easier to utilize the embedded scripts functionality. This allows you to embed scripts of any kind commandline scripts...

KB-ID 398
Category: Scripts
Applies to: 3.5 and later

The easiest way to accomplish this is by using the EventSentry application scheduler ampamp the Windows Shutdown.exehttps://docs.microsoft.com/enus/windowsserver/administration/windowscommands/shutdown application. Application Schedulerhttps://www.eventsentry.com/documentation/help/html/monitoringappscheduler.htm is a feature tha...

KB-ID 406
Category: Application Scheduler

The System Monitor service ampamp driver Sysmon for shorthttps://docs.microsoft.com/enus/sysinternals/downloads/sysmon logs various events mostly in response to process activity that occurs on a system to the MicrosoftWindowsSysmon/Operational event log. Sysmon events are similar to the 4688https://system32.eventsentry.com/secur...

KB-ID 437
Category: Application Scheduler
Applies to: 4.1 and later

When utilizing the application scheduler on some NonEnglish versions of Windows commands that output nonascii characters e.g. Umlaut in German may cause the following issues: NonAscii characters in event id 10200 are not displayed correctly in the event viewer NonAscii characters in event id 10200 may not be stored in the builtin...

KB-ID 452
Category: Monitoring